Skip to main content
Version: Development Snapshots

ELRS Custom Telemetry

Why Custom Telemetry

The ELRS (which uses the Crossfire protocol) has a limited array of parameters that can be transferred. Many of these values are not very applicable to a helicopter (as opposed to drones). Other values such as headspeed (quite important for our helicopters) are not available. In Rotorflight 2.0 returning some of our more important parameters back to the Tx was achieved by ELRS Telemetry Re-use however, this was also limited.

Custom telemetry has been implemented for ELRS in Rotorflight 2.1. This allows many more sensors that was previously not possible with CRSF. Currently there are over 100 sensors to choose from, and a maximum of 40 sensors can be used in total. With the ELRS configurable telemetry ratio, the sensors can be updated up to 20 times per second.

Note: ‘Telemetry Reuse’ (from Rotorflight 2) has been removed as it is no longer required

note

For elrs custom telemetry to work as expected it is essential to use elrs 3.5 or higher. Using lower versions will result in intermittent telemetry lost warnings.

If you still get warnings after upgrading your elrs to 3.5 or higher - reducing the frame rate on the rotorflight config page to a value lower than your elrs module will prevent the receiver being overrun by telemetry data.

Please choose to suit your Radio - EdgeTX or ETHOS

Rotorflight has great support for both EdgeTX and Ethos. Please choose your radio.